[wip] osc: Add TLS scanner periodic jobs for sandboxed-containers-operator by thejasn · Pull Request #79389 · openshift/release

thejasn · 2026-05-18T05:21:57Z

Add two 72h periodic jobs on the devel branch to verify TLS compliance of the sandboxed-containers operator stack with an active peer pod:

tls-scanner-default: baseline TLS scan (certs, ciphers, protocols)
tls-scanner-pqc: PQC readiness check (TLS 1.3 + ML-KEM/X25519MLKEM768)

Updates the OpenShift CI periodic configuration for the openshift/sandboxed-containers-operator devel periodics to add two TLS-scanner periodic jobs and related CI inputs, and tweaks peerpod parameterization.

Practical impact

Affects CI for the openshift/sandboxed-containers-operator repository (devel variant / periodics).
Adds two 72-hour periodic jobs that run the tls-scanner against a live peer Pod in the aws-sandboxed-containers-operator cluster profile:
- tls-scanner-default — baseline TLS scan (certs, ciphers, protocols).
- tls-scanner-pqc — PQC readiness scan (sets PQC_CHECK="true" to exercise TLS 1.3 + ML-KEM / X25519MLKEM768).
Both jobs run the sandboxed-containers-operator-e2e-aws workflow, use cluster_profile: aws-sandboxed-containers-operator, create a peer Pod named tls-scan-peerpod (runtimeClassName: kata-remote) in namespace openshift-sandboxed-containers-operator, wait up to 10m for readiness, run the scanner, then delete the Pod with a 5m timeout.
Shared environment and test settings include ENABLEPEERPODS="true", RUNTIMECLASS=kata-remote, SCAN_NAMESPACE=openshift-sandboxed-containers-operator, TEST_SCENARIOS=C00113, WORKLOAD_TO_TEST=peer-pods, AWS_REGION_OVERRIDE=us-east-2, TEST_TIMEOUT="90". tls-scanner-pqc additionally sets PQC_CHECK="true".

CI image and build inputs

Adds base_images.tls-scanner-tool (namespace: tls-scanner, name/tag: tls-scanner-tool).
Updates base_images.tests-private to namespace ci with tag "4.22".
Pins build_root.image_stream_tag to rhel-9-golang-1.25-openshift-4.21.
releases.latest.integration remains ocp/4.21.

Peerpod parameterization change

The peerpods parameter ConfigMap now accepts a PODVM_INSTANCE_TYPES env var (default "t3.medium") and documents supplying a comma-separated list of AWS instance types; the script generation now derives PODVM_INSTANCE_TYPES from that env var when set (falls back to "t3.medium").

Resources and other notes

Preserves global/default per-test resource requests (cpu: 100m, memory: 200Mi).
Change is CI YAML/configuration only (no exported/public code changes). Generator metadata records branch devel, org openshift, repo sandboxed-containers-operator, variant periodics.
PR comments show the author issued the periodic rehearsal command five times ("/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default").

Related to: rhjira#KATA-5101

coderabbitai · 2026-05-18T05:22:25Z

Walkthrough

Adds devel periodic CI for sandboxed-containers-operator: updates base_images (tests-private→ci:4.22, adds tls-scanner-tool), pins build_root/releases to ocp/4.21, sets default job resources, and adds two 72h TLS-scanner periodic jobs (default and PQC).

Changes

OpenShift Sandboxed Containers Operator Periodic Configuration

Layer / File(s)	Summary
Base images and release pins `ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml`	`base_images.tests-private` updated to `ci:4.22`; `base_images.tls-scanner-tool` added; `build_root.image_stream_tag` and `releases.latest.integration` pinned to `ocp/4.21`; default job resources set.
TLS scanner periodic job (default) `ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml`	Defines `tls-scanner-default` 72h periodic: creates `kata-remote` peer Pod, waits up to 10m, runs `tls-scanner-run`, and deletes the Pod (5m); per-step resource overrides included.
TLS scanner periodic job (PQC) `ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml`	Defines `tls-scanner-pqc` 72h periodic mirroring default flow with `PQC_CHECK: "true"` in environment.
Generated metadata `ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml`	Adds `zz_generated_metadata` for branch `devel`, org `openshift`, repo `sandboxed-containers-operator`, variant `periodics`.
Peerpods param-cm: instance types `ci-operator/step-registry/sandboxed-containers-operator/peerpods/param-cm/sandboxed-containers-operator-peerpods-param-cm-commands.sh`, `ci-operator/step-registry/sandboxed-containers-operator/peerpods/param-cm/sandboxed-containers-operator-peerpods-param-cm-ref.yaml`	Makes `PODVM_INSTANCE_TYPES` configurable via env var (default `t3.medium`) in ConfigMap generation and adds reference docs for providing a comma-separated list validated at startup.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

openshift/release#78981: Adds the tls-scanner-tool base image and wires TLS scanner CI workflows.

Suggested labels

rehearsals-ack

🚥 Pre-merge checks | ✅ 11 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (11 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR contains only CI infrastructure files (YAML configs and shell scripts), not Ginkgo test definitions. The check for stable test names is not applicable to this PR.
Test Structure And Quality	✅ Passed	PR contains no Ginkgo test files. Changes are CI/CD configuration (YAML) and shell scripts, not Go test code. Custom check is not applicable.
Microshift Test Compatibility	✅ Passed	PR adds CI configuration and shell scripts for periodic jobs, not Ginkgo e2e tests. The check applies only to new Ginkgo test code; this PR contains no Ginkgo test definitions.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR adds CI periodic job configurations and step registry definitions only. No Ginkgo e2e test code (It(), Describe(), etc.) is added. Custom check for SNO e2e test compatibility is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR contains only CI configuration (job definitions and test step registry files), not deployment manifests, operator code, or controllers. Custom check is not applicable.
Ote Binary Stdout Contract	✅ Passed	OTE check not applicable: PR modifies only CI configuration (YAML) and shell scripts, not OTE binary code with main(), init(), TestMain(), or suite setup functions.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR adds CI configuration/scripts, not Ginkgo e2e tests. Custom check only applies to new Ginkgo test additions (It(), Describe(), etc.), so it is not applicable here.
Title check	✅ Passed	The title is partially related to the changeset—it mentions TLS scanner periodic jobs but includes '[wip]' prefix and is less specific than the actual changes, which also include peerpods parameter ConfigMap modifications for PODVM_INSTANCE_TYPES.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

🧹 Nitpick comments (1)

ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml (1)
25-138: 🏗️ Heavy lift

Consider extracting duplicated Pod lifecycle steps to shared step-registry entries.

The two test definitions are 99% identical—they differ only in the PQC_CHECK environment variable (line 89). The entire Pod manifest (lines 42-64 vs 99-121), creation logic, wait command, and deletion logic are duplicated across both tests.

This duplication increases maintenance burden: any change to the Pod spec or lifecycle commands must be applied in two places, risking inconsistency.

Consider refactoring by:

Creating a shared step-registry entry for peer-pod creation/deletion

Parameterizing the Pod manifest via environment variables if needed

Passing test-specific environment variables (like PQC_CHECK) through the step configuration

This would reduce the ~110 lines to approximately half while preserving both test variants.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml`
around lines 25 - 138, Both periodic tests (as: tls-scanner-default and as:
tls-scanner-pqc) duplicate the peer-pod Pod manifest and lifecycle steps;
extract those into reusable step-registry entries and parameterize them. Create
shared step-registry steps (e.g., create-peer-pod and delete-peer-pod) that
accept env parameters like POD_NAME, SCAN_NAMESPACE (or NAMESPACE),
RUNTIMECLASS, IMAGE, and TIMEOUT, then replace the inline commands in both test
definitions with references to those steps; keep test-specific env (PQC_CHECK)
only in the top-level env for tls-scanner-pqc so the common steps read
parameters from the passed env. Ensure the step names match the existing ref
usages (ref: create-peer-pod and ref: delete-peer-pod) so workflow
sandboxed-containers-operator-e2e-aws continues to work.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In
`@ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml`:
- Around line 25-138: Both periodic tests (as: tls-scanner-default and as:
tls-scanner-pqc) duplicate the peer-pod Pod manifest and lifecycle steps;
extract those into reusable step-registry entries and parameterize them. Create
shared step-registry steps (e.g., create-peer-pod and delete-peer-pod) that
accept env parameters like POD_NAME, SCAN_NAMESPACE (or NAMESPACE),
RUNTIMECLASS, IMAGE, and TIMEOUT, then replace the inline commands in both test
definitions with references to those steps; keep test-specific env (PQC_CHECK)
only in the top-level env for tls-scanner-pqc so the common steps read
parameters from the passed env. Ensure the step names match the existing ref
usages (ref: create-peer-pod and ref: delete-peer-pod) so workflow
sandboxed-containers-operator-e2e-aws continues to work.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 9353e89e-afd5-4951-89ae-1c3d364881f0

📥 Commits

Reviewing files that changed from the base of the PR and between 6d4c827 and 86c7095.

⛔ Files ignored due to path filters (1)

ci-operator/jobs/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel-periodics.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (1)

ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml

thejasn · 2026-05-18T05:41:12Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default

openshift-merge-bot · 2026-05-18T05:41:15Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-05-18T10:09:19Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default

openshift-merge-bot · 2026-05-18T10:09:21Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-05-18T13:48:28Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default

openshift-merge-bot · 2026-05-18T13:48:31Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-05-19T04:09:06Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default

openshift-merge-bot · 2026-05-19T04:09:09Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-05-19T07:14:30Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default

openshift-merge-bot · 2026-05-19T07:14:33Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-05-20T17:18:18Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default

openshift-merge-bot · 2026-05-20T17:18:21Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-05-20T17:21:37Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default

openshift-merge-bot · 2026-05-20T17:21:40Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

coderabbitai

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml (1)
88-145: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Consider adding PODVM_INSTANCE_TYPES for consistency.

The tls-scanner-default test explicitly sets PODVM_INSTANCE_TYPES: t3.medium (line 37), but this test omits it. Since both tests enable peer pods (ENABLEPEERPODS: "true"), explicitly setting the instance type in both tests would improve consistency and reduce the risk of divergent behavior if defaults change.
📝 Proposed addition
     env:
       AWS_REGION_OVERRIDE: us-east-2
       ENABLEPEERPODS: "true"
       PQC_CHECK: "true"
+      PODVM_INSTANCE_TYPES: t3.medium
       RUNTIMECLASS: kata-remote
       SCAN_NAMESPACE: openshift-sandboxed-containers-operator
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml`
around lines 88 - 145, The tls-scanner-pqc periodic job omits
PODVM_INSTANCE_TYPES while tls-scanner-default sets PODVM_INSTANCE_TYPES:
t3.medium; add PODVM_INSTANCE_TYPES: t3.medium to the job's env block (near
ENABLEPEERPODS, PQC_CHECK, RUNTIMECLASS, etc.) in the tls-scanner-pqc definition
(as: tls-scanner-pqc) so both peer-pods tests explicitly use the same instance
type.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In
`@ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml`:
- Around line 88-145: The tls-scanner-pqc periodic job omits
PODVM_INSTANCE_TYPES while tls-scanner-default sets PODVM_INSTANCE_TYPES:
t3.medium; add PODVM_INSTANCE_TYPES: t3.medium to the job's env block (near
ENABLEPEERPODS, PQC_CHECK, RUNTIMECLASS, etc.) in the tls-scanner-pqc definition
(as: tls-scanner-pqc) so both peer-pods tests explicitly use the same instance
type.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 3cf72de6-0f4c-4518-9da5-8adaf33dc2a4

📥 Commits

Reviewing files that changed from the base of the PR and between 5edcfdb and e588601.

📒 Files selected for processing (3)

ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__periodics.yaml
ci-operator/step-registry/sandboxed-containers-operator/peerpods/param-cm/sandboxed-containers-operator-peerpods-param-cm-commands.sh
ci-operator/step-registry/sandboxed-containers-operator/peerpods/param-cm/sandboxed-containers-operator-peerpods-param-cm-ref.yaml

thejasn · 2026-05-21T04:29:00Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default

openshift-merge-bot · 2026-05-21T04:29:03Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-05-21T07:39:15Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc

openshift-merge-bot · 2026-05-21T07:39:18Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-06-29T11:30:11Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc

openshift-merge-bot · 2026-06-29T11:33:54Z

@thejasn: pj-rehearse could not automatically process this event because the request waited in queue for longer than 5 minutes. Use /pj-rehearse to trigger rehearsals manually.

thejasn · 2026-06-29T11:34:32Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc

openshift-merge-bot · 2026-06-29T11:35:11Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

openshift-merge-bot · 2026-06-29T11:37:29Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-06-30T04:17:59Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc

openshift-merge-bot · 2026-06-30T04:18:01Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-06-30T04:18:13Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default

openshift-merge-bot · 2026-06-30T04:18:16Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-06-30T12:45:55Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc

openshift-merge-bot · 2026-06-30T12:45:57Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Add two 72h periodic jobs on the devel branch to verify TLS compliance of the sandboxed-containers operator stack with an active peer pod: - tls-scanner-default: baseline TLS scan (certs, ciphers, protocols) - tls-scanner-pqc: PQC readiness check (TLS 1.3 + ML-KEM/X25519MLKEM768) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Thejas N <thn@redhat.com>

thejasn · 2026-07-02T06:52:51Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc

openshift-ci · 2026-07-02T06:52:53Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: thejasn
Once this PR has been reviewed and has the lgtm label, please assign snir911 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-merge-bot · 2026-07-02T06:52:55Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

openshift-merge-bot · 2026-07-02T06:55:33Z

[REHEARSALNOTIFIER]
@thejasn: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc	N/A	periodic	Periodic changed
periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default	N/A	periodic	Periodic changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

openshift-merge-bot · 2026-07-02T06:56:07Z

@thejasn: requesting more than one rehearsal in one comment is not supported. If you would like to rehearse multiple specific jobs, please separate the job names by a space in a single command.

thejasn · 2026-07-02T06:59:08Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc

openshift-merge-bot · 2026-07-02T06:59:11Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

thejasn · 2026-07-03T05:05:11Z

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc

openshift-merge-bot · 2026-07-03T05:05:13Z

@thejasn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

openshift-ci · 2026-07-03T12:05:28Z

@thejasn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/rehearse/periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default	`6616a6e`	link	unknown	`/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-default`
ci/rehearse/periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc	`6616a6e`	link	unknown	`/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-periodics-tls-scanner-pqc`

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

openshift-ci Bot requested review from gkurz and wainersm May 18, 2026 05:22

coderabbitai Bot reviewed May 18, 2026

View reviewed changes

thejasn force-pushed the thn/osc-tls-scanner branch from 86c7095 to 31b37be Compare May 18, 2026 09:30

thejasn force-pushed the thn/osc-tls-scanner branch from 31b37be to 5edcfdb Compare May 19, 2026 07:11

thejasn changed the title ~~osc: Add TLS scanner periodic jobs for sandboxed-containers-operator~~ [wip] osc: Add TLS scanner periodic jobs for sandboxed-containers-operator May 20, 2026

openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 20, 2026

coderabbitai Bot reviewed May 20, 2026

View reviewed changes

thejasn force-pushed the thn/osc-tls-scanner branch from e588601 to f55ed6e Compare May 21, 2026 04:21

thejasn force-pushed the thn/osc-tls-scanner branch from 0fdecc6 to c35f8f0 Compare June 29, 2026 11:28

thejasn force-pushed the thn/osc-tls-scanner branch from 11eb891 to 6616a6e Compare July 2, 2026 06:52

Uh oh!

Conversation

thejasn commented May 18, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot commented May 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested labels

❌ Failed checks (1 warning)

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

thejasn commented May 18, 2026

Uh oh!

openshift-merge-bot Bot commented May 18, 2026

Uh oh!

thejasn commented May 18, 2026

Uh oh!

openshift-merge-bot Bot commented May 18, 2026

Uh oh!

thejasn commented May 18, 2026

Uh oh!

openshift-merge-bot Bot commented May 18, 2026

Uh oh!

thejasn commented May 19, 2026

Uh oh!

openshift-merge-bot Bot commented May 19, 2026

Uh oh!

thejasn commented May 19, 2026

Uh oh!

openshift-merge-bot Bot commented May 19, 2026

Uh oh!

thejasn commented May 20, 2026

Uh oh!

openshift-merge-bot Bot commented May 20, 2026

Uh oh!

thejasn commented May 20, 2026

Uh oh!

openshift-merge-bot Bot commented May 20, 2026

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

thejasn commented May 21, 2026

Uh oh!

openshift-merge-bot Bot commented May 21, 2026

Uh oh!

thejasn commented May 21, 2026

Uh oh!

openshift-merge-bot Bot commented May 21, 2026

Uh oh!

thejasn commented Jun 29, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 29, 2026

Uh oh!

thejasn commented Jun 29, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 29, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 29, 2026

Uh oh!

thejasn commented Jun 30, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 30, 2026

Uh oh!

thejasn commented Jun 30, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 30, 2026

Uh oh!

thejasn commented Jun 30, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 30, 2026

Uh oh!

thejasn commented Jul 2, 2026

Uh oh!

thejasn commented May 18, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented May 18, 2026 •

edited

Loading